home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19941031-19941221
/
000382_news@columbia.edu_Wed Dec 7 14:04:55 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA12173
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Fri, 9 Dec 1994 23:58:43 -0500
Received: by apakabar.cc.columbia.edu id AA19901
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Fri, 9 Dec 1994 23:58:42 -0500
Newsgroups: comp.protocols.kermit.misc
Path: news.columbia.edu!spcuna!solaris.cc.vt.edu!news.mathworks.com!usenet.eel.ufl.edu!usenet.cis.ufl.edu!caen!hearst.acc.Virginia.EDU!murdoch!fulton.seas.Virginia.EDU!esh6h
From: esh6h@fulton.seas.Virginia.EDU (Erik Hatcher)
Subject: Re: Server side renames - still not solved!
Message-Id: <D0G1s8.CBo@murdoch.acc.Virginia.EDU>
Sender: usenet@murdoch.acc.Virginia.EDU
Organization: University of Virginia
References: <D0CyFn.4sv@murdoch.acc.virginia.edu> <3c2240$5uh@apakabar.cc.columbia.edu>
Date: Wed, 7 Dec 1994 14:04:55 GMT
Lines: 48
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3c2240$5uh@apakabar.cc.columbia.edu>,
Jeffrey Altman <jaltman@watsun.cc.columbia.edu> wrote:
>Erik:
>
>The answer appears to be that at this time server side RENAME
>is not possible unless you lower the security barriers a bit
>which you do not want to do.
No I'm not willing to compromise our system security to
rename a file! :)
>The only suggestion that I have for you is to perform the rename
>on the client before you send the file. Or just send the file
>with the name is it supposed to the saved under from the very
>start.
>
>SEND oldname newname
>
>has exactly the same result as
>
>SEND oldname
>REMOTE RENAME oldname newname
But it is not "exactly" the same result, is it?
One creates a file called "newname" from the start.
The other only creates "newname" after the entire
file is successfully sent (assuming that REMOTE RENAME
isn't done "if failure").
The reason I want/need REMOTE RENAME is so that my
automatic process to pick up received files on the
remote end, doesn't try to pick up a file being sent
or not successfully sent. It only picks up files
with the name REC_*.* and they are sent as SENDING_*.*.
Frank mentioned that he'll put it in the next version,
so I'm fine with that! Thanks a million Frank!
BTW, not being pushy, but how often do new versions
get released?
Erik
--
Erik Hatcher + "But every now and then we just have
http://fulton.seas.virginia.edu/~esh6h | to howl with the wolves."
| - Werner Heisenberg
---------------------------------------+-------------------------------------